🐛 fix: Group Scope Picker and Name Resolution Past 200 Groups - #115

The scope picker's create view fetched a single list capped at the backend's 200 per request maximum and filtered it client side via cmdk, so in deployments with more groups (issue #96 reports 1500+ from Entra SSO sync) most groups could never be found or selected. The groups section now searches server side with a debounced query and offset pagination through a new useGroupSearch hook built on the existing getGroupsFn search/limit/offset support, mirroring the GroupsTab pattern.

getAvailableScopesFn built its group name map from that same first page of 200 groups, so existing group scopes outside the window displayed their raw Mongo ObjectId instead of the group name. It now resolves names for exactly the group principalIds that have config overrides via GET /api/admin/groups/:id, fetched in small parallel batches, and falls back to the principalId when an individual group cannot be fetched.

The create view filtered each backend page against existing configurations after pagination, while totalPages still described every group. A page whose groups were all configured rendered the global "all groups already have configurations" empty state even when later pages held eligible groups, and searches could report no matches for the same reason. Configured groups are now rendered as disabled entries with an "Already configured" badge instead of being filtered out, so the page contents always match the server totals and the empty states only describe truly empty result sets. Covered by ScopeSelector.test.tsx, which renders a fully configured first page and asserts disabled entries plus a reachable second page; both tests fail against the previous filtering.

Also moves the GroupSearch hook contract from useGroupSearch.ts into src/types/hooks.ts per the repository convention that locally defined interfaces live in src/types and are referenced through the @/types namespace import.

The back control in the scope create view only flipped showCreate, so useGroupSearch kept its page and filter and reopening the view rendered the previous search and page. The dialog-level resetState cleared the input through the debounced onSearchChange, so the debounced query value and page reset lagged the emptied input by the debounce delay and a reopen inside that window could still query with the stale search.

useDebouncedFilter gains a synchronous reset that cancels any pending commit and restores both values at once, useGroupSearch exposes it (clearing the page in the same call, mirrored in the GroupSearch contract in src/types/hooks.ts), and ScopeSelector routes both the back control and resetState through a shared closeCreate that resets the search state without debounce lag. The back control also gets an accessible name. Regression tests: reopening create after a search starts from page 1 unfiltered without issuing a stale search request (ScopeSelector.test.tsx), and reset clears search and page synchronously with no request for a pending debounced value (useGroupSearch.test.tsx).

…Input

With keepPreviousData, rows from the previous page or search stayed clickable while a new group page was in flight, so a click during a slow fetch could create a configuration for a group outside the currently requested results. Group rows are now disabled while groupSearch.isFetching, alongside the existing creating and already-configured states, and the dimmed wrapper also blocks pointer events. Covered by a gated-fetch test that holds the list request open and asserts stale rows are disabled until it resolves.

The 200 character search clamp previously applied only inside getGroupsFn, so the visible input and the react-query key kept the full text while the request sent a truncated one, letting the displayed query diverge from the queried one and letting distinct long searches with a shared 200 character prefix duplicate equivalent requests under different cache keys. useGroupSearch now clamps in onSearchChange so value, debounced value, query key, and request all agree, with the server-fn clamp kept as a backstop; MAX_SEARCH_LENGTH is exported from the groups module as the single source of the limit. The truncation test now asserts the input value is clamped as well.

Typing a new search updates the visible query immediately while the request waits out the 300ms debounce, so isFetching stayed false and rows from the previous query remained clickable against a search they no longer match. The hook now exposes isSearchPending (raw versus debounced mismatch) and the create view gates rows on it alongside isFetching.

… GroupsTab Search

While a debounced search was fetching, keepPreviousData kept the old multi-page total visible and the paginator stayed clickable even though the rows were disabled, so clicking an old later page started the searched query at that offset and a single-page result stranded the view on an empty out-of-range page with the paginator gone. The create view now dims the paginator and ignores page changes while a fetch or debounce is pending, and useGroupSearch additionally clamps the page back to the last valid page whenever a settled total drops below it, so no code path can leave the view stranded.

useGroupSearch also discarded query errors, rendering a failed groups request as an empty list. The hook now exposes isError and refetch through the GroupSearch contract and the create view renders the existing com_error_load_groups message with a retry button in place of the list, hiding the paginator while errored.

The Groups management tab calls groupsQueryOptions directly and never goes through useGroupSearch, so its controlled input and query key kept a search beyond 200 characters while the server fn truncated it in transport. Its search handler now clamps with the shared MAX_SEARCH_LENGTH before state and debounce, keeping displayed and queried text identical, with the server-fn clamp still in place as a backstop.

Regression coverage: pagination clicks are ignored mid-search and the view settles on the searched first page, an out-of-range page clamps back to the last valid page, a failed fetch renders the retryable error state and retry recovers, and the GroupsTab input value matches the queried search at 200 characters. All four fail before this change.